Update `x2a` workspace to commit `4526035` for backstage `1.45.3` on branch `main` by github-actions[bot] · Pull Request #2222 · redhat-developer/rhdh-plugin-export-overlays

github-actions · 2026-04-06T13:11:05Z

Update x2a workspace at commit redhat-developer/rhdh-plugins@4526035 for backstage 1.45.3 on branch main.

This PR was created automatically.

⚠️ Manual re-approval required
An override exists at workspaces/x2a/backstage.json. This upgrade is a Best-Effort match.
Since the previous version was manually verified to work against the target Backstage version, please review and test again before merging.
Click on the following link to see the source diff it introduces: redhat-developer/rhdh-plugins@06c72e9...4526035.

Before merging, you need to export the workspace dynamic plugins as OCI images,
and if possible test them inside a RHDH instance.

To do so, you can use the /publish instruction in a PR review comment.
This will start a PR check workflow to:

export the workspace plugins as dynamic plugins,
publish them as OCI images
push the oci-images in the GitHub container registry with a PR-specific tag.

…branch `main`

openshift-ci · 2026-04-06T13:11:18Z

Hi @github-actions[bot]. Thanks for your PR.

I'm waiting for a redhat-developer member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

github-actions · 2026-04-06T13:16:24Z

Publish workflow has completed with failure.

Publishing process

❌ Plugins with errors during export or container image publishing:

plugins/x2a
Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a-backend:pr_2222__1.3.0
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-x2a:pr_2222__0.3.0

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.48.3).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/x2a	1.45.3	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

✅ All metadata files validated successfully.

openshift-ci · 2026-04-07T09:19:18Z

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

github-actions · 2026-04-08T18:05:36Z

Successfully updated file versions.jsonfrom branch main into this PR in commit 51442d3

github-actions · 2026-04-08T18:25:26Z

Publish workflow has completed with failure.

Publishing process

❌ Plugins with errors during export or container image publishing:

plugins/x2a
Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a-backend:pr_2222__1.3.0
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-x2a:pr_2222__0.3.0

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.48.3).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/x2a	1.45.3	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

✅ All metadata files validated successfully.

github-actions · 2026-04-09T19:03:56Z

Successfully updated file versions.jsonfrom branch main into this PR in commit 836480e

github-actions · 2026-04-09T19:12:12Z

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a:pr_2222__1.2.0
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a-backend:pr_2222__1.3.0
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-x2a:pr_2222__0.3.0

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.48.3).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/x2a	1.45.3	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

✅ All metadata files validated successfully.

No E2E tests available for this workspace.

github-actions · 2026-04-13T15:46:53Z

A new workspace commit b4dd783f4b0258857a3ce51b3650456da68e5caa has been discovered (match type: 'best-effort').
You can update this PR with the latest discovered workspace source commit.

To do so, you can use the /update-commit instruction in a PR review comment.

github-actions · 2026-04-13T15:53:24Z

Publish workflow has completed with success.

Publishing process

✅ Finished successfully.

Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a:pr_2222__1.2.0
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a-backend:pr_2222__1.3.0
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-x2a:pr_2222__0.3.0

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.48.3).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/x2a	1.45.3	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

✅ All metadata files validated successfully.

No E2E tests available for this workspace.

github-actions · 2026-04-14T10:57:57Z

Successfully updated file versions.jsonfrom branch main into this PR in commit f9d54bc

github-actions · 2026-04-14T11:07:10Z

Publish workflow has completed with failure.

Publishing process

✅ Finished successfully.

Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a:pr_2222__1.2.0
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a-backend:pr_2222__1.3.0
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-x2a:pr_2222__0.3.0

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.49.4).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/x2a	1.45.3	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

❌ Found 3 validation error(s):

File	Kind	Message
red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-x2a.yaml	mismatch	OCI tag mismatch: expected "bs_1.49.4__0.3.0" but got "bs_1.48.3__0.3.0"
red-hat-developer-hub-backstage-plugin-x2a-backend.yaml	mismatch	OCI tag mismatch: expected "bs_1.49.4__1.3.0" but got "bs_1.48.3__1.3.0"
red-hat-developer-hub-backstage-plugin-x2a.yaml	mismatch	OCI tag mismatch: expected "bs_1.49.4__1.2.0" but got "bs_1.48.3__1.2.0"

davidfestal · 2026-04-20T11:55:42Z

/update-commit

…branch `main`

github-actions · 2026-04-20T12:00:33Z

Recommended actions after the commit update:

Best-Effort upgrade with unknown backstage compatibility: After testing the plugins against the target backstage version, you should add a backstage.json file in the workspace folder to override the known Backstage compatibility to be the target Backstage version.

sonarqubecloud · 2026-04-20T12:01:04Z

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

github-actions · 2026-04-20T12:01:45Z

Update Commit workflow has completed with failure.

github-actions · 2026-04-20T12:02:41Z

Publish workflow has completed with failure.

Publishing process

✅ Finished successfully.

Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a:pr_2222__1.2.0
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a-backend:pr_2222__1.3.0
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-x2a:pr_2222__0.3.0

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.49.4).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/x2a	1.45.3	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

❌ Found 3 validation error(s):

File	Kind	Message
red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-x2a.yaml	mismatch	OCI tag mismatch: expected "bs_1.49.4__0.3.0" but got "bs_1.48.3__0.3.0"
red-hat-developer-hub-backstage-plugin-x2a-backend.yaml	mismatch	OCI tag mismatch: expected "bs_1.49.4__1.3.0" but got "bs_1.48.3__1.3.0"
red-hat-developer-hub-backstage-plugin-x2a.yaml	mismatch	OCI tag mismatch: expected "bs_1.49.4__1.2.0" but got "bs_1.48.3__1.2.0"

github-actions · 2026-04-20T12:09:18Z

Publish workflow has completed with failure.

Publishing process

❌ Plugins with errors during export or container image publishing:

plugins/x2a-mcp-extras
Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a:pr_2222__1.2.1
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a-backend:pr_2222__1.4.0
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-x2a:pr_2222__0.3.1
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a-dcr:pr_2222__0.2.0

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.49.4).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/x2a	1.45.3	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

✅ All metadata files validated successfully.

github-actions · 2026-04-20T12:15:58Z

Publish workflow has completed with failure.

Publishing process

❌ Plugins with errors during export or container image publishing:

plugins/x2a-mcp-extras
Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a:pr_2222__1.2.1
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a-backend:pr_2222__1.4.0
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-x2a:pr_2222__0.3.1
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a-dcr:pr_2222__0.2.0

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.49.4).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/x2a	1.45.3	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

✅ All metadata files validated successfully.

davidfestal · 2026-04-20T15:30:41Z

/update-commit

github-actions · 2026-04-20T15:37:27Z

Update Commit workflow has completed with failure.

github-actions · 2026-04-20T15:43:38Z

Publish workflow has completed with failure.

Publishing process

❌ Plugins with errors during export or container image publishing:

plugins/x2a-mcp-extras
Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a:pr_2222__1.2.1
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a-backend:pr_2222__1.4.0
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-x2a:pr_2222__0.3.1
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a-dcr:pr_2222__0.2.0

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.49.4).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/x2a	1.45.3	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

✅ All metadata files validated successfully.

davidfestal · 2026-04-20T16:16:06Z

/update-commit

github-actions · 2026-04-20T16:22:59Z

Update Commit workflow has completed with success.

github-actions · 2026-04-20T16:30:10Z

Publish workflow has completed with failure.

Publishing process

❌ Plugins with errors during export or container image publishing:

plugins/x2a-mcp-extras
Published container images:
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a:pr_2222__1.2.1
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a-backend:pr_2222__1.4.0
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-x2a:pr_2222__0.3.1
- ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-x2a-dcr:pr_2222__0.2.0

Backstage-incompatible workspaces

Some workspaces have a backstage version (in sources or in their overlay folder) which is incompatible with the target Backstage version (1.49.4).
1 incompatible workspaces, 0 of which are mandatory:

Folder	Backstage version	Mandatory	Info
workspaces/x2a	1.45.3	⚪	BS Version History

How to fix

You have 3 main options:

Use the already-opened PR : For automatically-discovered workspaces, there might already be an automatically-opened PR that updates the commit to the target backstage version (Automatic PR link in column 4 above): just publish the plugins and test them from the PR by following the PR instructions.
Manually update the workspace commit :
- Find a newer commit, with a backstage version compatible with the target backstage version :__*
  - Backstage version history available: A BS Version History link might be available in column 4: in the workspace source repository, it points to the list of commits touching the backstage.json file. This would help you finding out whether this workspace has a commit that has been published for the target backstage version.
  - No info available: If no information is is provided in column 4, the backstage.json probably does not exist in workspace sources. You would have to look deeper into the newer commits of workspace sources, possibly in the low-level dependencies in the package.json files, to find out a commit with an underlying backstage version compatible with the target backstage version.
- Then, in the overlay repository, update the repo-ref field of the source.json file to the new source commit, and remember to also change the repo-backstage-version field to the corresponding compatible backstage version.
No compatible commit : If the workspace sources contain no compatible newer commit ( == a commit that provides a backstage.json version compatible with the target backstage), but the current workspace commit is known to work with the target backstage version, then you can override the declared backstage version compatibility for this workspace commit in the overlay repository: add a backstage.json file at the root of the overlay workspace folder with the desired target backstage version. This would require full testing of the workspace plugins on the target backstage though.

Metadata Validation

✅ All metadata files validated successfully.

Update x2a workspace to commit 93e17f5 for backstage 1.45.3 on …

c3e19d0

…branch `main`

github-actions bot requested review from a team, gashcrumb and kadel as code owners April 6, 2026 13:11

openshift-ci bot added the needs-ok-to-test label Apr 6, 2026

github-actions bot added the workspace-update PR modifies files in an existing workspace label Apr 6, 2026

openshift-ci bot added the needs-rebase label Apr 7, 2026

chore: sync versions.json from main

51442d3

chore: sync versions.json from main

836480e

github-actions bot added the needs-commit-update label Apr 13, 2026

chore: sync versions.json from main

f9d54bc

Update x2a workspace to commit 4526035 for backstage 1.45.3 on …

2881f9b

…branch `main`

github-actions bot changed the title ~~Update x2a workspace to commit 93e17f5 for backstage 1.45.3 on branch main~~ Update x2a workspace to commit 4526035 for backstage 1.45.3 on branch main Apr 20, 2026

github-actions bot removed the needs-commit-update label Apr 20, 2026

Conversation

github-actions bot commented Apr 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci bot commented Apr 6, 2026

Uh oh!

github-actions bot commented Apr 6, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

openshift-ci bot commented Apr 7, 2026

Uh oh!

github-actions bot commented Apr 8, 2026

Uh oh!

github-actions bot commented Apr 8, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

github-actions bot commented Apr 9, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

github-actions bot commented Apr 13, 2026

Uh oh!

github-actions bot commented Apr 13, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

github-actions bot commented Apr 14, 2026

Uh oh!

github-actions bot commented Apr 14, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

davidfestal commented Apr 20, 2026

Uh oh!

github-actions bot commented Apr 20, 2026

Uh oh!

sonarqubecloud bot commented Apr 20, 2026

Quality Gate passed

Uh oh!

github-actions bot commented Apr 20, 2026

Uh oh!

github-actions bot commented Apr 20, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

github-actions bot commented Apr 20, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

github-actions bot commented Apr 20, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

davidfestal commented Apr 20, 2026

Uh oh!

github-actions bot commented Apr 20, 2026

Uh oh!

github-actions bot commented Apr 20, 2026

Publishing process

Backstage-incompatible workspaces

Metadata Validation

Uh oh!

davidfestal commented Apr 20, 2026

Uh oh!

github-actions bot commented Apr 20, 2026

Uh oh!

github-actions bot commented Apr 20, 2026

Publishing process

github-actions bot commented Apr 6, 2026 •

edited

Loading